Skip to content

v0.13.0
Compare
Choose a tag to compare
@calmh calmh released this 17 May 12:05
v0.13.0
This tag was signed with the committer’s verified signature.
calmh Jakob Borg
GPG key ID: 49F5AEC0BCE524C7
Learn about vigilant mode.
2ea22b1

Syncthing v0.13.0 "Copper Cockroach"

Upgrade Notes

  • v0.13 is not protocol compatible with v0.12.
  • The database format has changed. It will be migrated without rescan on first startup, but the first startup may take longer than usual.

Major Changes Since v0.12

Devices now announce files that are in progress of being downloaded, in addition to those that are already complete. This means a device can serve parts of a file to other devices before it has completed the download itself.

Folder labels are now distinct from the folder ID. The intention is for the label to be human readable and for the ID to be machine readable and unique. When upgrading, folder IDs are not changed. However when creating new folders Syncthing will suggest a random, unique folder ID.

When receiving a connection attempt from an unknown device Syncthing will now show the name of that device, not only it's ID.

Syncthing will now manage port mappings on NAT-PMP compliant routers, in addition to the existing UPnP support.

Minor Changes and Improvements

  • Ignored files can now be tagged with the prefix (?d) to indicate that Syncthing may delete these files if they remain when deleting a directory. Ignore patterns use less memory by default.
  • The address for sync connections, both the listening side and for remote devices, can now be made IPv4- or IPv6-only. Use the tcp4:// or tcp6:// schemes to specify one or the other. The default tcp:// is still dual stack. Additionally, relays are now treated as listen addresses and set in the same configuration setting.
  • The folder settings dialog has been cleaned up.
  • The environment variable ALL_PROXY_NO_FALLBACK can be set to disable falling back to direct connections in the absence of a working proxy.
  • Many, many bug fixes.

Known Issues

  • The "Syncing" complete percentage for remote devices may erroneously display more than 100% (i.e. 156% or 297%) while a remote device is still synchronizing.
Assets 2